-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved detection of line endings in ChunkBuffer #42
base: master
Are you sure you want to change the base?
Conversation
Added carriage return + line feed (\n\r) as possible line ending to 'readLine()'
@jordancamara can you take a look at this? |
Is there someone with write access? If so i will update the PR. |
It seems like everyone with write access have gone silent. I'd love to see this merged. It solved an issue for me. |
Seems like I don't have the rights to merge too, I would like someone to update the pods too, to fix some bugs Starscream. May be forking is the only way for now |
I have updated this and the other pull request into my fork, and updated the pods too. I didn't test much, though everything seems to work fine. Not much changes in the code, however I will be testing all the new changes this week. If anyone finds an issue then please let me know. |
Shouldn't it be |
still issue is there. |
Objective C code working in swift (using bridge header) - No reconnection issues and other. Dear @auther please check on swift version. Thank for your help |
Added carriage return + line feed (\n\r) as possible line endings to 'readLine()'.
Otherwise if the server delivers a response like:
data: {...}\n\r data: {}
the response cannot be parsed correctly in 'ServerSentEventsTransport.open()'